Skip to content

Add clear ASCII warning banner summarizing blind-zone and lead time#12

Open
dewanggaabdullah wants to merge 1 commit into
tylrcc:mainfrom
dewanggaabdullah:develop
Open

Add clear ASCII warning banner summarizing blind-zone and lead time#12
dewanggaabdullah wants to merge 1 commit into
tylrcc:mainfrom
dewanggaabdullah:develop

Conversation

@dewanggaabdullah

Copy link
Copy Markdown

What and why

This PR addresses Issue #7 by adding a high-visibility ASCII warning banner inside sim_main() in tremormesh/cli.py.

The new banner visually isolates and highlights the two critical metrics requested: blind-zone radius and warning lead time, making the output much more scannable for engineers at a glance when an alert is triggered. All existing lines have been kept exactly as they were to ensure that CI pipelines and automated testing remain completely unaffected.

Checklist

  • pytest -q passes locally
  • If I changed the detector, I updated both tremormesh/stalta.py and 4_Firmware/node/node.ino, plus the tests
  • No generated artifacts committed (plots, build output, binaries)
  • Docs updated if behaviour or interfaces changed

Notes for reviewers

Live Output Screenshots

I have prepared two visual approaches for the banner depending on your preference for the terminal UI:

Case 1: Compact Informative Box (Currently Active in Code)

This version provides a clean structured summary with an actionable evacuation notice for the simulation broadcast trigger.

Screenshot from 2026-05-31 21-11-46

Case 2: High-Visibility Large Text-Art (Alternative Layout)

This version uses a larger text-art style for the "WARNING" header to maximize attention.

Screenshot from 2026-05-31 21-09-30

The code is currently using Case 1 as I felt it keeps the CLI clean, but please let me know which style you prefer! I'm happy to swap it to Case 2 if you like that better. Thank you!

@dewanggaabdullah

Copy link
Copy Markdown
Author

Hi @tylrcc, I would like to let you know that my PR is ready for review. I look forward to your further instructions

@dewanggaabdullah

dewanggaabdullah commented Jun 14, 2026

Copy link
Copy Markdown
Author

Hi @tylrcc , I’m just following up on the task I completed last week. I wanted to drop a gentle reminder in case it slipped under your radar. I'm a bit concerned that leaving this PR open for too long might lead to disruptive merge conflicts. I would really appreciate some clear feedback so I know whether I need to make further adjustments to the code, or if my approach isn't quite what you're looking for. Here is the link:#12

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant